Test: add a repo-level release version consistency test - #297

Please ensure you have read the contribution guide before creating a pull request.

Link to Issue or Description of Change

1. Link to an existing issue (if applicable):

N/A

2. Or, if no issue exists, describe the change:

Problem: release-please-config.json puts the root package, core, dev and integrations in one linked-versions group, so they must always publish the same version. Nothing enforced that. A release that bumps core but skips dev keeps every per-package test green, because each package only checks itself. Only a test that reads across packages catches the drift.

Solution: One integration test reads the four package.json files and .release-please-manifest.json at runtime and asserts they declare one version. It compares them as a single record, so the failure diff names every file that drifted. A second case asserts the packages it checks are exactly the linked-versions group, so a new workspace cannot join the release group and stay unchecked. No version literal appears in the test.

This branch was 52 commits behind main. I rebased it onto 9360bf24 and force-pushed. The diff is one new file.

Collision check: I listed all 666 open PRs on the fork and inspected every version- or release-adjacent one. No other PR touches tests/integration/release/. PRs #258, #417 and #619 add per-package src/version.ts tests under core/test/ and dev/test/. That is a different concern and a disjoint file set.

Note on JSON.parse: the parsed value is typed unknown and narrowed by a type guard. Typing it directly as the expected shape would be an unchecked assertion, which the repository guidelines forbid.

Testing Plan

Please describe the tests that you ran to verify your changes. This is required for all PRs that are not small documentation or typo fixes.

Unit Tests:

• I have added or updated unit tests for my change.
• All unit tests pass locally.

npx vitest run --project integration tests/integration/release/version_consistency_test.ts
# Test Files 1 passed (1) | Tests 2 passed (2)
npm run build      # clean
npx eslint tests/integration/release/version_consistency_test.ts     # clean
npx prettier --check tests/integration/release/version_consistency_test.ts
# All matched files use Prettier code style!
npx tsc --noEmit   # zero diagnostics name this file

tsc --noEmit does report pre-existing errors in other test files, for example core/test/a2a/agent_card_test.ts and core/test/utils/live_connection_utils_test.ts. They are on main already and ts:check is not part of the validation workflow, so I left them alone.

The file lands in the integration vitest project, which npm run test:coverage runs. That is the script the validation workflow calls, so the test gates CI.

Proof each test can fail. I mutated the repository files one at a time and confirmed each mutation turns the suite red. I reverted every one with git checkout and re-ran the suite green.

The third mutation isolates the semver guard: with all eight entries equal, the record comparison still passes and only the guard fails.

Manual End-to-End (E2E) Tests:

npm install
npm run build
npx vitest run --project integration tests/integration/release/version_consistency_test.ts

To watch it fail, change any version field in dev/package.json and re-run.

Checklist

• I have read the CONTRIBUTING.md document.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.